Systems and methods for processing benefits

ABSTRACT

Systems and methods for processing, for example, childcare benefits include: issuing a benefit card to a childcare customer; receiving a start time for childcare service at a childcare provider, the start time recorded by using the benefit card at a terminal located at the childcare provider at the start of childcare service; receiving an end time for childcare service at the childcare provider, the end time recorded by using the benefit card at a terminal located at the childcare provider at the end of childcare service; computing the childcare benefit eligibility based on the start time, the end time and benefits available for the childcare customer; and paying the childcare provider a payment based on the computed benefit eligibility.

DESCRIPTION

[0001] This application claims priority under 35 U.S.C. § 119 based onU.S. Provisional Application No. 60/399,153, filed Jul. 30, 2002, thecomplete disclosure of which is incorporated herein by reference.

TECHNICAL FIELD

[0002] This invention is related to information management, and moreparticularly to systems and methods for managing payments, budgetingaccounts, and reporting finances of services such as childcare services.

DISCUSSION OF RELATED ART

[0003] Federal and state governments are responsible for protecting thewelfare of its citizens. As a consequence, programs have beenestablished that offer financial assistance or benefits to thosecitizens whose income meets or falls below the poverty line. Inimplementing these programs, some state governments provide subsidies orgrants for services such as childcare services. Over time, however, atleast one study has uncovered rampant fraud and abuse in the areas ofrecord keeping and billing among a number of childcare providers.Moreover, this study indicated that a more efficient means of trackingand monitoring the records of all children receiving governmentsponsored childcare is needed. Still further, this study showed thatstate sponsored childcare programs lack a sufficient number of qualifiedchildcare providers, and that the retention rate of qualified childcareproviders needs improvement.

[0004] Many such problems in the childcare systems result from the sheeramount of time and energy required by the childcare system participants(e.g., administrators, service providers, and funding agencies) indealing with massive amounts of paperwork involved in tracking childcareproviders, determining eligibility of children for care, and maintainingand processing attendance records in a timely manner. Further, thesecomplex processes not only result in waste and frustration forparticipants, but also provide ample opportunities for fraud.

[0005] In light of the aforementioned problems encountered by existinggovernment sponsored childcare services there is a need to provide anefficient systems and methods for managing service providing systemssuch as childcare providing systems.

SUMMARY

[0006] Methods and systems of the present invention enable benefitsadministrators and service providers to meet financial and recordmanagement obligations in an efficient and timely manner.

[0007] Consistent with the invention, some embodiments of the inventionprovide a method for processing benefit payments to service providers.The method for processing childcare benefit payments comprises the stepsof issuing a benefit token with a unique machine-readable identifier toa customer; reading the identifier from the benefit token at a terminallocated at the provider at the beginning of a service session togenerate a start time; reading the identifier from the benefit token atthe terminal at the end of the service session to generate an end time;transmitting a transaction record including the start time and the endtime to a processing system; computing benefit payment based on thestart time, the end time, and an eligibility criteria; and transmittingthe benefit payment to the services provider. In some embodiments, theservices provider may be a provider of childcare services. In someembodiments, computing the benefit payment may also be based on specificbusiness rules.

[0008] It is to be understood that both the foregoing generaldescription and the following detailed description are exemplary andexplanatory only and are not restrictive of the invention, as claimed.

[0009] The accompanying drawings, which are incorporated in andconstitute a part of this specification, illustrate several embodimentsof the invention and together with the description, serve to explain theprinciples of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] In the drawings:

[0011]FIG. 1 shows a block diagram illustrating an overview of achildcare processing system consistent with methods and systems of thepresent invention;

[0012]FIG. 2 shows an exemplary childcare processing environmentconsistent with methods and systems of the present invention;

[0013]FIG. 3 shows a diagram illustrating a benefit card consistent withmethods and systems of the present invention;

[0014]FIG. 4 shows a diagram illustrating a transaction recordconsistent with methods and systems of the present invention;

[0015]FIG. 5 shows a diagram illustrating a terminal consistent withmethods and systems of the present invention;

[0016]FIG. 6 shows a block diagram of an exemplary computing systemconsistent with methods and systems of the present invention;

[0017]FIG. 7 shows a diagram illustrating a childcare processing systemconsistent with methods and systems of the present invention;

[0018]FIG. 8 shows a diagram illustrating various modules of thechildcare processing system consistent with methods and systems of thepresent invention;

[0019]FIG. 9 shows a diagram illustrating various managementapplications of the childcare processing system consistent with methodsand systems of the present invention;

[0020]FIG. 10A shows a diagram illustrating an exemplary screen relatedto account setup consistent with methods and systems of the presentinvention;

[0021]FIG. 10B shows a diagram illustrating an exemplary screen relatedto childcare customer information management consistent with methods andsystems of the present invention;

[0022]FIG. 10C shows a diagram illustrating an exemplary screen relatedto issuance of a new benefit card consistent with methods and systems ofthe present invention;

[0023]FIG. 10D shows a diagrams illustrating an exemplary screen relatedto replacement of a benefit card consistent with methods and systems ofthe present invention;

[0024]FIG. 10E shows a diagram illustrating an exemplary screen relatedto issuance of a childcare benefit to a childcare provider consistentwith methods and systems of the present invention;

[0025]FIG. 10F shows a diagram illustrating an exemplary screen relatedto transaction history consistent with methods and systems of thepresent invention;

[0026]FIG. 10G shows a diagram illustrating an exemplary screen relatedto messaging for childcare providers and customers consistent withmethods and systems of the present invention;

[0027]FIG. 11 shows a schematic diagram listing exemplary reports thatmay be generated consistent with methods and systems of the presentinvention;

[0028]FIGS. 12A and 12B illustrate exemplary reports consistent withmethods and system of the present invention;

[0029]FIG. 13 shows a flow diagram illustrating an exemplary method forprocessing childcare benefits consistent with methods and systems of thepresent invention;

[0030]FIG. 14 shows a flow diagram illustrating another exemplary methodfor processing childcare benefits consistent with methods and systems ofthe present invention;

[0031]FIG. 15 shows a flow diagram illustrating an exemplary method formanaging childcare benefits consistent with methods and systems of thepresent invention;

[0032]FIG. 16 shows a flow diagram illustrating another exemplary methodfor managing childcare benefits consistent with methods and systems ofthe present invention;

[0033]FIG. 17 shows a flow diagram illustrating a redundant arrangementfor processing childcare benefits consistent with methods and systems ofthe present invention;

[0034]FIG. 18 shows a flow diagram illustrating an exemplary method forrecording a childcare service transaction consistent with methods andsystems of the present invention; and

[0035]FIG. 19 shows a flow diagram illustrating an exemplary method forgenerating a report consistent with methods and systems of the presentinvention.

DESCRIPTION OF THE EMBODIMENTS

[0036] Reference will now be made in detail to the exemplary embodimentsconsistent with the invention, examples of which are illustrated in theaccompanying drawings. Wherever possible, the same reference numberswill be used throughout the drawings to refer to the same or like parts.The childcare processing system disclosed below is an example of abenefits processing system. The examples disclosed herein illustratesome embodiments of the present invention and are not intended to limitapplicability of the invention to other benefits programs.

[0037] The disclosed benefits processing system is a distributedarchitecture-based electronic childcare processing system. Accordingly,it may be implemented using object-oriented programming techniques, suchas JAVA, distributed databases, and an Internet browser-based front-end.Several users, including federal staff, state staff, county staff,childcare providers, administrators, and childcare customers mayinteract with the childcare processing system without having specializedsoftware on their computers. Childcare providers and customers maycommunicate with the system using telephones and/or terminals, forexample, which may be located at the childcare providers' site.

[0038] Overview

[0039] Methods and systems according to the present invention aredirected to better management of childcare benefits and records from thechildcare customer to a childcare benefits administrator. The customermay be a benefits recipient in need of childcare and eligible forfederal, state, or local support, such as payment for childcareservices.

[0040] Initially, the customer applies for a transaction token in theform of, for example, a benefit card. In order to receive the benefitcard, the customer provides personal information to the benefitsadministrator, including information regarding employment, education,training, and other requested details. The customer then receives abenefit card, having a unique machine-readable identifier, that tracksthe customer's use of childcare and provides for benefits, such aspartial payment of childcare fees, based on customer eligibility.

[0041] A benefit card is associated with each customer and may storeinformation about the customer relating to entitlement to benefits. Thebenefit card may also be linked to a credit card or deposit account,from which payment of additional fees associated with childcare notcovered by the benefits provided to that customer may be drawn.

[0042] A terminal, typically located at an approved childcare providersite, provides an interface between the benefits provided, the childcareprovider, and the customer through the benefit card. The customer swipesthe benefit card through the terminal at the beginning and end of eachchildcare provider session. The terminal may also include an entry padfor entry of codes or additional data. The terminal creates atransaction record of the use of childcare. The terminal may alsofacilitate a payment transaction, such as a co-payment associated withthe childcare or an overtime payment. The combination of the terminaland the benefit card allow for the easy tracking of attendance at achildcare provider. The transaction record stores information, includingcustomer information, date, location, start time for care, end time forcare, and other relevant transaction information. A transaction recordmay include one transaction or many transactions for one child, onecustomer, or one location.

[0043] The terminal is connected through a network to a childcareprocessing system, which receives transaction records from a pluralityof terminals. The transaction records may be transmitted to thechildcare processing system at regular intervals, such as daily, weekly,or monthly. In particular, the childcare processing system processesbenefits payments based on the transaction records. The benefitspayments are calculated using time and attendance data of customers atthe childcare provider. The benefits payments may also factor inspecific state or federal childcare rules applicable to a particularcustomer. The childcare processing system may be used by the benefitsadministrator to generate payments to childcare providers or customers.The childcare processing system may also be operated by a third partythat also transmits invoices for benefits amounts for childcare serviceto the benefits administrator.

[0044] Through receipt of transaction records, the childcare processingsystem may also generate a number of reports. The reports may includecase management reports, individual childcare use reports, auditreports, overall use tracking reports, and other types of reports thatmay be generated using data from the transaction records. The reportsmay be viewed by the customer, childcare provider, or benefitsadministrator in paper form or using the Internet. Though the use ofelectronic tracking, the childcare processing system can provide for theefficient management of childcare benefits.

[0045]FIG. 1 provides an overview of the general structure of achildcare processing environment 100. Childcare processing environment100 includes a customer 110, a benefit card 120, a benefitsadministrator 130, a childcare provider 140, a terminal 150, and atransaction record 160.

[0046] Customer 110 is a benefits recipient who is eligible forchildcare benefits for one or more children. Benefit card 120 is a cardissued by benefits administrator 130 to customer 110 for use in thechildcare processing environment 100. Benefit card 120 storesinformation about customer 110. Benefits administrator 130 may be thefederal, state, county, or private group that sponsors childcarebenefits for eligible participants.

[0047] Childcare provider 140 provides one or more services to qualifiedcustomers 110. Several childcare providers 140, for example, may belocated in the same building, but typically they would at least occupydifferent rooms. Each childcare provider 140 may be managed by one ormore different economic entities, or some or all of childcare providers140 may be managed by the same economic entity. In fact, a differentindividual may manage each childcare provider 140. Examples of servicesthat may be provided by one or more of childcare providers 140 includeday care, medical, counseling, or other services associated withchildren.

[0048] The site of childcare provider 140 includes a terminal 150, whichconnects childcare provider 140 with a childcare processing system 200to facilitate execution of client transactions and calculation ofpayment data based on those transactions over a predefined period oftime. Client transactions can, for example, include recording beginningand ending times for the duration of services, validating clientidentity, and verifying eligibility for the services requested.Childcare provider 140 further stores and outputs the respectivefinancial data and transaction information as a transaction record 160,which can be transferred to a childcare processing system 200.

[0049]FIG. 2 illustrates an embodiment of childcare processingenvironment 100 with a childcare processing system 200 consistent withmethods and systems of the present invention. Childcare processingsystem 200 may be an Electronic Payment Processing and InformationControl (“EPPIC”) system, connected via a network 205 to customers 110_(A-N). Any number of customers 110A-N may be connected to childcareprocessing system 200 through network 205. Childcare processing system200 is further connected, via a network 206, to terminals 150 _(A-N).Each of terminals 150 _(A-N) is located at a corresponding childcareprovider 140 _(A-N). Childcare processing system 200 is furtherconnected, via network 207 to benefits administrator 130. Benefitsadministrator 130 may include connections to federal, state, and countyproviders (not shown). Although only a limited number of participantsare depicted in FIG. 2, additional participants, such as third partyprocessors, federal, state, and county offices may be connected tochildcare processing system 200 through various networking environments.

[0050] Networks 205, 206 and 207 may be any appropriate mechanismpermitting communication among the various components. Examples ofnetworks 205, 206 and 207 include the Internet, telephony networks,private networks, virtual private networks, local area networks,metropolitan area networks, wide area networks, ad hoc networks, statenetworks, frame-relay networks, or any other mechanism for permittingcommunication between remote sites, regardless of whether the connectionis wired or wireless. Thus, the present invention can be used in anyenvironment where information may be exchanged by any means among thevarious components childcare processing environment 100.

[0051] Benefit Card

[0052]FIG. 3 shows a diagram illustrating transaction token 120consistent with methods and systems of the present invention. Token 120may be in the form of a plastic card with a magnetized strip ofinformation, a smart card, an RF transponder, or any other device thatmay be used for machine readable retrieval and storage of benefitsinformation.

[0053] Each prospective customer 110 completes an application todetermine whether they qualify for childcare benefits. Once customer 110completes the application process, an administrative institution throughbenefits administrator 130 authorizes or denies the client participationin the childcare program. If benefits administrator 130 authorizescustomer 110 to receive subsidized childcare, the responsible benefitsadministrator 130 opens a benefits account for the customer, includingproviding a unique identifier, and sends customer 110 a transactiontoken, such as benefit card 120 shown, for example, in FIG. 3. Benefitcard 120 can include a magnetic stripe 310 for electronically storingdata, including the identifier associated with the account of customer110, as was discussed above.

[0054] Benefit card 120 can store personal benefits criteria associatedwith the level of assistance provided to customer 110, as is specifiedin the account of customer 110. Customer 110 swipes benefit card 120 ata terminal 150 located at the site of care provider 140 at the start andend of each session during which childcare services are rendered. Thestart and stop times may be stored in terminal 150, on benefit card 120,and/or transmitted through network 206 to childcare processing system200, where it is accessible to benefits administrator 130. In someembodiments, benefit card 120 is linked with customer 110's financialaccount separate from the benefits account, facilitating the transfer offunds from the financial account to cover a co-payment or other amountnot covered by the benefits approved for customer 110 at the time ofchildcare service.

[0055] Transaction Record

[0056]FIG. 4 is a diagram of a transaction record 160 created atterminal 150. Transaction record 160 stores information, includingcustomer information, date, location, start time for care, end time forcare, co-payment amount, and other relevant transaction information.Transaction record 160 may include information for one or moretransactions. Transaction record 160 may refer to one customer 110 or toone or more children of customer 110 or may include all information fora provider 140.

[0057] Transaction record 160 can include any information that recordsthe time in and time out parameters for service provided at childcareprovider 140. Further, transaction record 160 can be formatted in anyway. In some embodiments, transaction record 160 includes fixed fieldsfor transmitting data regarding the transaction. In some embodiments,transaction record 160 includes one or more of the following fields:record type; authorization number; authorization case number;authorization person number; contract number; transaction number; swipedate; swipe time; swipe type; current date; current time; completioncode; paid amount; paid date; card number; user number; copay amount;pay source; reason code; deduction amount; transaction phone number; POSphone number; last used date; reference number; maximum number of paidFT days; Maximum number of paid PT days; Maximum number of absent days;previous period FT day count; previous period PT day count; currentperiod FT day count; current period PT day count; previous period FTdays remaining; previous period PT days remaining; current period FTdays remaining; current period PT days remaining; previous periodcumulative copay; current period cumulative copay; copay amount; copaypercent; previous period remaining copay; current period remainingcopay; copay effective date; part time rate; full time rate; copay flag;last modified date; last modified by. Descriptions of these variousexample fields are provided in Table I below.

[0058] The record type field can indicate one of several types ofrecords for transmission between childcare provider 140 and childcareprocessing system 200. For example, the following record types may beindicated numerically in transaction record 160: swipes, manual overrideswipes, manual entry, administrative terminal entry, administrativeterminal adjustments, payment to provider, absence payments, clientinactivity report, card status entries, declined transactions, andpending transactions. Descriptions of these record types are provided inTable II below. Records of these various types are transmitted betweenterminal 150 and benefits administrator 130 through child careprocessing system 200, as is illustrated in FIG. 2. TABLE I Examples ofFields that may be present in record 160. Data Field Description RecordType The record type field indicates the type of record 160. Variousrecord types are described in Table II. Authorization Number Theauthorization number field contains a unique number created by benefitsadministrator 130 at the time customer 110 is authorized to receiveservices at childcare provider 140. Authorization Case The authorizationcase number field contains Number the case number assigned by benefitsadministrator 130 associated with authorization of services at childcareprovider 140. Authorization Person The authorization person number filedcontains Number a number assigned to the person (i.e., child) associatedwith a particular attendance transaction. Each person associated withcard 120 who is eligible to receive services at childcare provider 140is assigned a person number unique to the case number for card 120.Contract Number The contract number field contains information indicatedthe contract between benefits administrator 130 and childcare provider140 for provision of services to customer 110. Transaction Number Thetransaction number field contains a number associated with theparticular transaction. Transaction numbers may be assigned by childcareprocessing system 200 for utilization in terminal 150. Swipe Date Theswipe data field provides the date of services provided by childcareprovider 140. In some embodiments, the date is provided by terminal 150or can be manually entered at terminal 150 to be a date prior to thedate of data entry. Swipe Time The swipe time field provides the time ofattendance and is typically provided by terminal 150 as the time card120 is inserted into terminal 150. Swipe Type The swipe type fieldindicates whether the attendance is being recorded as an “in” or an“out” type, i.e. when customer 110 arrives for service or leaves afterservice. Current Date The current date field indicates the date thetransaction indicated in record 160 was recorded. Current Time Thecurrent time field indicates the date the transaction indicated inrecord 160 was recorded. Completion Code The completion code fieldindicates the authorization code returned to childcare provider 140after customer 110 inserts card 120. An indication of whether thetransaction is approved, denied or pending, with additional detail, maybe provided. Paid Amount The paid amount field indicates the monetaryamount paid to childcare provider 140 to compensate for provision ofservices. Paid Date The paid date field indicates the payment date toprovider. Card Number The card number field indicates the identificationof card 120 and can be captured by terminal 150 from card 120. UserNumber The user number field indicates a number associated with a user'sinput of a transaction record 160 through a device other than one ofterminal 150. CoPay Amount The copay amount field indicates the monetaryamount that has accumulated against the indicated transaction. PaySource The pay source field indicates the source of funds for payment ofthe benefits associated with the transaction indicated by record 160.Reason Code The reason code field indicates the reason for anyadjustment in the transaction or rejection of the transaction indicatedby record 160. Deduction Amount The deduction amount field indicates themonetary amount deducted from a payment to childcare provider 140 inorder to recoup past overpayments to childcare provider 140. TransactionPhone The transaction phone number field indicates Number the phonenumber associated with terminal 150. POS Phone Number The POS phonenumber field indicates the phone number associated with childcareprovider 140, where terminal 150 is located. Last Used Date The lasedused date field indicates the date that card 120 was last used in atransaction. Reference Number The reference number field indicates areference number assigned by benefits administrator 130 associated withan adjustment to childcare provider 140. Max Number of Paid FT The MaxNumber of Paid FT Days field Days indicates the number of full-time daysof subsidized service that child indicated in the authorization personnumber field is authorized to receive during the calendar month. MaxNumber of Paid PT The Max Number of Paid PT Days field Days indicatesthe number of part-time days of subsidized service that a childindicated in the authorization person number field is authorized toreceive during the calendar month. Max Number of Absent The Max Numberof Absent Days field Days indicates the maximum number of days for whichchildcare provider 140 may receive payment for services even if thechild indicated in the authorization person number field is absentduring the calendar month. Previous Period FT Day The previous period FTday count field Count indicates the number of full time days of day carethat the child indicated in the authorization person number fieldreceived during the previous calendar month. Previous Period PT Day Theprevious period PT day count field Count indicates the number of parttime days of day care that the child indicated in the authorizationperson number field received during the previous calendar month. CurrentPeriod FT Day The current FT day count field indicates the Count numberof full time days of service that the child indicated in theauthorization person number field has received during the currentcalendar month. Current Period PT Day The current period PT day countfield indicates Count the number of part time days of service that thechild indicated in the authorization person number field has receivedduring the current calendar month. Previous Period FT Days The previousperiod FT days remaining field Remaining indicates the unused number offull-time days of service that the child indicated in the authorizationperson number field has available from the previous calendar month.Previous Period PT Days The previous period PT days remaining fieldRemaining indicates the unused number of part-time days of service thatthe child indicated in the authorization person number field hasavailable from the previous calendar month. Current Period FT Days Thecurrent period FT days remaining field Remaining indicates the unusednumber of full-time days of day care that the child indicated in theauthorization person number field has available for the current calendarmonth. Current Period PT Days The current period PT days remaining fieldRemaining indicates the unused number of part-time days of day care thatthe child indicated in the authorization person number field hasavailable for the current calendar month. Previous Period The previousperiod cumulative copay field Cumulative CoPay indicates the monetaryamount of the copay that accumulated for the child indicated in theauthorization person number field during the previous calendar month.Current Period The current period cumulative copay field CumulativeCoPay indicates the monetary amount of the copay that accumulated forthe child indicated in the authorization person number field during thecurrent calendar month. CoPay Amount The copay amount field indicatesthe monetary value of the copay that is due from customer 110 tochildcare provider 140 for the child indicated in the authorizationperson number field during the previous calendar month. CoPay PercentThe copay percent field indicates the percentage of the services ratethat should be used to calculate the daily copy due from customer 110 tochildcare provider 140. Previous Period The previous period remainingcopay field Remaining CoPay indicates the monetary value of theuncollected copy from customer 110 associated with the child indicatedin the authorization person number field during the previous calendarmonth. Current Period The current period remaining copay field RemainingCoPay indicates the monetary value of the uncollected copy from customer110 associated with the child indicated in the authorization personnumber field during the current calendar month. CoPay Effective Date Thecopay effective date field indicates the earliest date that copay is duefrom customer 110 to childcare provider 140 for the effectiveauthorization. Part Time Rate The part-time rate field indicates themonetary value due to childcare provider 140 for one day of part-timeservices for the child indicated in the authorization person field withthe current authorization. Full Time Rate The full-time rate fieldindicates the monetary value due to childcare provider 140 for one dayof full-time services for the child indicated in the authorizationperson field with the current authorization. CoPay Flag The copay flagfield indicates whether or not there is a copay allocated to the caseassociated with this authorization. Last Modified Date The last modifieddate field indicates the date that the case data associated with thisauthorization was last modified. Last Modified By The last modified byfield indicates the user identification of the benefits administrator130 who last modified data associated with this authorization.

[0059] TABLE II DESCRIPTION OF EXAMPLE RECORD TYPES Record TypeDescription of Record Type swipes record A swipes record type includesan attendance transaction, including a date/time stamp in and out anddata identifying and authorizing customer 110 for the services atchildcare provider 140. A swipes record is typically created whencustomer 110 utilizes card 120 in terminal 150. Manual Override A manualoverride swipes record is a record of an Swipes attendance transactionthat was not captured at the time service was provided at childcareprovider 140 and that was entered through terminal 150 manually withoutcard 120. Manual Entry A manual entry record type indicates anattendance transaction captured when customer 110 enters an identifyingcard number and attendance data manually at terminal 150. AdministrativeAn administrative terminal entry record type Terminal Entry indicates amanual entry of an attendance transaction entered by benefitsadministrator 130. Administrate Terminal An administrative terminaladjustment record type Adjustments indicates an adjustment to anexisting record created by benefits administrator 130. Payment toProvider A payment to provider record type indicates a detailed paymentrecord to childcare provider 140. Absence payments An absence paymentrecord type indicates payment to childcare provider 140 for periodswhere children covered by card 120 are absent. Client Inactivity Aclient inactivity report record type indicates a Report detailed list ofcase numbers where card 120 has not been utilized in a set period oftime (for example 14 days). Card Status Entries A card status entryrecord type indicates the status of card 120, for example active orinactive. Declined Transactions A declined transactions record typeindicates Swipe type entries where service is declined by benefitsadministrator 130. Pending Transactions A pending transactions recordtype indicates that customer 110 has applied for services at childcareprovider 140 but that those services have not yet been approved bybenefits administrator 130.

[0060] As shown in FIG. 4, a simplified example of transaction record160 is shown. The fields indicated in FIG. 4 includes the following: theuser qualities, which includes information about the authorization ofservices afforded to customer 110; the identification and authorizationfor the child receiver services at childcare provider 140; the time-inparameter indicating the start of services; the time-out parameterindicating the conclusion of services; the location identification ofchildcare provider 140; the date of the services; and the amount ofcopay provided by customer 110 for those services.

[0061] Terminal

[0062]FIG. 5 illustrates a block diagram of an embodiment of terminal150 consistent with methods and systems of the present invention.Terminal 150 includes an interaction device 510 and a local computer520.

[0063] Terminal 150 electronically executes transactions (i.e., buildsrecord 160 from available date stored on card 120 or in computer 520)and processes transaction information to calculate payment data over apredefined period of time. Interaction device 510 is connected to sendpayment data and transaction information read from card 120 to localcomputer 520 and in some embodiments to write or modify information oncard 120. Interaction device 510 can include a card reader 513, a keypad515, and a display 517. In some embodiments, display 517 may be combinedwith a display terminal that is also coupled with computer 320.

[0064] Card reader 513 includes electronic circuitry that enablesinteraction device 210 to extract identification information frombenefit card 120 (not shown). Although, FIG. 5 illustrates card reader513 as a raised structure on the top portion of interaction device 510,it should be apparent that card reader 513 could be located at variouspositions on the structure of interaction device 513. Furthermore, cardreader 513 may have any appropriate design configuration.

[0065] Keypad 515 includes a plurality of buttons that may be labeledwith at least one alphanumeric character, which character may bepresented to a user on display 517 when a button is depressed. Thebuttons may also perform other functions identified by functionaldescriptions inscribed on keypad 515 in close proximity to therespective button. Button 3, for example, may be labeled with theletters D, E, and F, and the number 3. Moreover, the functionaldescription “AM” may be located beneath button 3, which informs a userthat button 3 may be used when defining the time of day. In someembodiments, keypad 515 may be a separate keyboard that is coupled tocomputer 520.

[0066] Display 517 can be a standard liquid crystal display device. Inresponse to a user's input or a processing event, display 517 presentsany of a number of alphanumeric characters or text messages to the user.

[0067] Local computer 520 stores payment data and transactioninformation received from interaction device 510. Local computer 520includes software for organizing and processing payment data andtransaction information. Local computer 520 may, for example, includesoftware to generate an annual billing report for benefits administrator130. Local computer 520 preferably provides an annual billing reportaccessible by or transferable to childcare processing system 130 throughnetwork 206 so that benefits administrator 130 may access theinformation from childcare processing system 130 over network 207.Moreover, local computer 520 further preferably generates reports inresponse to a request or query submitted to child care provider system200 over a network coupled to child care provider system 200. Therequest may come from benefits administrator 130 or from otheradministrative institutions authorized to access that information inchild care provider system 200. Embodiments of terminal 150 may combineinteraction device 510 and computer 520 into one functional unit.

[0068] After customer 110 submits benefit card 120 to card reader 513,display 517 can be utilized to prompt customer 110 for any additionalinformation required to complete the requested transaction. As discussedabove, card reader 513 may obtain personal benefits information ofcustomer 110 from benefit card 120. In some embodiments, a personalidentification number (PIN) or other form of authorization may berequired to ensure that a customer 110 is in fact the one using benefitcard 120.

[0069] Customer 110 verifies attendance at childcare provider 140, forexample, by using keypad 515 to input personal benefits information asprompted by display 517. After inputting the personal information,customer 110 uses keypad 517 to input additional information forcompleting the transaction as directed by computer 520 through display517.

[0070] Exemplary Computing System

[0071]FIG. 6 shows a block diagram of an exemplary computing system 600,consistent with an embodiment of the invention. Computing system 600 mayrepresent, for example, the internal components of computer 520 orchildcare processing system 200. By way of example, a program or set ofinstructions to run the childcare processing system 200 may beimplemented in computing system 600.

[0072] Computing system 600 may include a number of components, such asa processor or central processing unit (CPU) 610, a memory 620, anetwork interface 630, I/O devices 640, and/or a display 630. Suchcomponents may be interconnected by a system bus 660. CPU 610 may be amicroprocessor such as the Pentium® family of microprocessorsmanufactured by Intel Corporation. However, any other suitablemicroprocessor, micro-, mini-, or mainframe computer may be used, suchas a micro-controller unit (MCU), or a digital signal processor (DSP).

[0073] Memory 620 may include a random access memory (RAM), a read-onlymemory (ROM), a video memory, mass storage, and/or cache memory such asfixed and removable media (e.g., magnetic, optical, or magnetic opticalstorage systems or other available mass storage technology). Memory 620stores support modules such as, for example, a basic input/output system(BIOS), an operating system (OS), a program library, a compiler, aninterpreter, and/or a text-processing tool. Support modules arecommercially available and can be installed on computing system 600 bythose of skill in the art. For simplicity, these modules are notillustrated. Further, memory 620 may contain an operating system, anapplication routine, a program, such as a web browser program, anapplication-programming interface (API), and/or other instructions forperforming methods consistent with embodiments of the invention.

[0074] Network interface 630, examples of which include Ethernet,dial-up telephone and/or other conventional data port connections, maybe used to communicate with other devices through, for example, acommunication network (not shown). Computing system 600 may also receiveinput via input/output (I/O) devices 640, which may include a keyboard,pointing device, or other like input devices. Computing system 600 mayalso provide output via input/output (I/O) devices 640, which mayinclude interface device 510. Computing system 600 may also presentinformation and interfaces, such as a care application, via display 650to customer 110.

[0075] Bus 660 may be a bi-directional system bus. For example, bus 660may contain thirty-two address bit lines for addressing a memory 620 andthirty-two bit lines across which data is transferred among thecomponents. Alternatively, multiplexed data/address lines may be usedinstead of separate data and address lines.

[0076] Childcare Processing System

[0077]FIG. 7 is a diagram illustrating a childcare processing system200, consistent with methods and systems of the present invention. Asshown the childcare processing system may include a computing platform600, a database server 740, and a benefits database 730. Computingplatform 600 may further comprise applications 710, HTTP server 712, JSPengine 714, terminal messaging module 716, and Operating System 718.HTTP server 712 may provide automatic file processing ability using, forexample, an Extended Markup Language (“XML”) processor that mayautomatically process files received from a government entity. In someembodiments, for example, the received file may comply with an XMLschema and relying upon that schema an XML processor may extract recordslocated in the file.

[0078] The file may be at least one of a childcare customer accountsetup file, a childcare customer account update file, and a childcarecustomer update file, or a childcare provider account setup file, achildcare provider account update file, and a childcare provider updatefile. By processing any of these files account setup, account update,and benefits processing and payments may be processed. Automaticprocessing of the file may further include acknowledging a receipt ofthe file, validating a format of the file; and processing the recordslocated in the file. Thus, for example, processing of the file mayinclude extracting the relevant information from the file and updatingdatabases related to benefits information, such as benefits database730.

[0079] HTTP server 712 may be any HyperText Transport Protocolcompatible server, such as Apache Web Server, Microsoft IIS, or NetscapeEnterprise Server. Although FIG. 7 depicts a HTTP-based system, one mayuse any equivalent system that enables remote devices to accessfunctionality located on the childcare processing system.

[0080] JSP Engine 714 may include Java Server Pages-related technology(a technology from Sun Microsystems) permitting delivery of dynamiccontent to the users of childcare processing system 200. In someembodiments, Java language from Sun Microsystems may be used forscripting applications 710. JSP Engine 714 may further have access toSun Microsystem's J2EE platform for accessing the relevant softwarelibraries/modules. Other similar technologies, such as Active ServerPages (from Microsoft) may also be used. Additionally, CGI scripts orsimilar technologies that do not necessarily separate page design fromprogramming logic may also be used.

[0081] Terminal messaging module 716 may provide messaging functionalitysuch as ISO 8583 messaging between a terminal and childcare processingsystem 200. Such messaging may be accomplished over X.25 and IPprotocols or other appropriate protocols.

[0082] Operating system 718 may provide an interface between the varioussoftware modules of computing platform 600 and hardware associated withthe computing platform. Operating system 718 may be implemented usingSun Microsystem's Solaris operating system. It may also be implementedusing other appropriate operating systems such as UNIX, Linux, MicrosoftNT, HP-UX, AIX, or any other operating system that may interface thesoftware modules with the hardware associated with computing platform600.

[0083] Database server 740 may be any database server program, such asOracle 9i from Oracle that may be used to provide access to benefitsdatabase 730. Benefits database 730 may be a single database ordistributed over multiple databases. Although FIG. 7 shows only onedatabase, childcare processing system 200 may either include or connectto other databases as well.

[0084]FIG. 8 shows various examples of applications 710 implemented bychildcare processing system 200. Referring now to FIG. 8, applications710 may include software components for calculating benefits includingbusiness rule handling 811, day counter and absent day algorithms 812,part time benefits 813, full time benefits 814, user interface 815,manual claim processing 816, and management 817. The functionalityillustrated by these components may be combined or distributed furtherinto sub-components. Additional functionality may be added usingadditional software components. A business rule indicates a limitationon making payments and may be dictated by the state or the entity thatprovides funding for the benefit. For example, a business rule may limitthe amount of monetary compensation provided to a particular childcareprovider 140 in a period of time.

[0085]FIG. 9 shows examples various management applications 817.Management applications 817 may comprise software components includingan account management component 950, a card management component 952, abenefit management component 954, a transaction management component956, reconciliation management component 958, a payment managementcomponent 960, a report management component 962, and a user managementcomponent 964. The functionality provided in these components may becombined or distributed further into sub-components. Additionally, morefunctionality may be added using additional software components.

[0086] Interfaces with Childcare Processing System

[0087]FIG. 10A shows an exemplary screen related to establishing abenefits account for customer 110 or childcare provider 140. Accountmanagement component 950 may provide account creation for a childcarecustomer 110 or childcare provider 140. Thus, for example, benefitsadministrator 130, an authorized user of childcare processing system200, may establish benefits to a customer 110 to receive services from achildcare provider 140. As has been indicated above, a case number 1001is assigned to the authorization of services from childcare provider 140by benefits administrator 140. Accordingly benefits administrator 140may add a case with a certain case number 1001, assign it to one of theavailable programs that supplies benefits 1002, designate a case type1003 and continue 1004 with processing. Further, as shown in FIG. 10B,benefits administrator 140, who may be any authorized user of childcareprocessing system 200, may provide relevant information 1010 concerningthe new account with customer 110, which then may be stored, forexample, in benefits database 730 shown in FIG. 7.

[0088] Card management component 952 may provide functionalityassociated with managing benefit card 120. Card management component 952may include, among other things, functions associated with issuing newcards, activating the newly issued cards, replacing existing cards (forexample damaged or lost cards), changing a card's status, displaying thehistory of a card (for example, showing all current and prior cardnumbers with replacement date and status), assigning an authorizedrepresentative and/or protective payee to a food stamp or a cashaccount, issuing a PIN associated with a particular card, and allowingchildcare customer 110 s to change PIN's, for example, using a POSterminal 150 or an ATM. As illustrated in FIG. 10C, card managementcomponent 952 may include issuance of a new card 1022. Accordingly,benefits administrator 130, identified by a caseworker 1020, may issue acard 120 to a childcare customer 110, based on information 1010. Onceselected for issuance childcare processing system 200 may requireconfirmation before issuing card 120, for example by selecting “OK” in aconfirmation window 1024. Additionally, as depicted in FIG. 10D, cardmanagement 952 may further permit replacement of a lost or damaged card120 by entering appropriate information into replacement window 1030.

[0089] Referring again to FIG. 9, benefit management component 954 mayprovide functionality associated with managing benefits for variouschildcare customers 110. Benefit management component 954 may include,among other things, issuing new benefits, canceling existing benefits,and converting between benefits provided for customer 110. Benefitsinclude authorization for childcare payment and/or any other governmentsponsored childcare benefits provided to either childcare provider 140or directly to childcare customer 110 for childcare services. As shownin FIG. 10E, benefits administrator 130 may specify a particularbenefits program, amount of the benefit, and any other relevantinformation and authorize the benefit to childcare customer 110.Accordingly, as shown in FIG. 10E, benefit type, benefit amount, and itseffective date may be specified in benefits window 1040. Issuance ofbenefits may be confirmed in confirmation window 1042.

[0090] With reference to FIG. 9, transaction management component 956may provide functionality associated with tracking transactions relatedto a particular childcare customer 110, a particular benefit, or aparticular benefit program. Transaction management component 956 relatesto transactions involving a single childcare customer 110 ortransactions involving a childcare provider 140. Childcare customertransaction management may include displaying summary information onevery use by any of customers 110 of a childcare provider 140 anddisplaying specific detailed information for each use. Childcareprovider 140 transactions may include displaying summary information onevery transaction for the childcare provider 140 by the date selectedand displaying specifics on any particular transaction. Thus, forexample, as illustrated in FIG. 10F, benefits administrator 130 mayinvestigate a transaction history, illustrated in history window 1070,of a particular childcare customer 110. Alternatively, benefitsadministrator 130 may investigate a transaction history for a particularchildcare provider 140.

[0091]FIG. 10G illustrates a message provided by childcare processingsystem 200 in response to an inquiry from either a childcare customer110 or childcare provider 140. Childcare processing system 200 maydisplay at least one electronic message concerning the inquiry tochildcare customer 110 through a graphical user interface. The at leastone electronic mail message may be displayed in response to an inquiryfrom the childcare customer 110. Alternatively, it may be displayed evenwithout any inquiry from the childcare customer 110. For example, theelectronic message may provide updated information concerning benefitswithout being prompted by the childcare customer 110.

[0092] Referring again to FIG. 9, user management component 964 mayinclude functionality related to managing user accounts, for example,adding a recipient message, modifying, and deleting user accounts. Itmay also include functionality related to adding, modifying, anddeleting login privileges for various users (e.g., benefitsadministrators 130) of childcare processing system 200.

[0093] Reports

[0094] Report management component 962 may provide functionality relatedto generating reports, viewing reports, and printing reports. It mayalso permit retrieval of archived data. FIG. 11 illustrates variousreports 1100 that may be generated in report management component 962.Reports 1100 may include account activity reports 1110, terminalactivity reports 1120, clearing reports 1130, database value reports1140, administrative reports 1150, financial reports 1160, paymentreports 1170 and data activity reports 1180. Account activity report1110 may generate a report that reflects all transactions related to acustomer 110, an authorized person associated with customer 110, or achildcare provider 140, for example, (i.e., an account) for a particularday. It may also provide information concerning all account relatedtransactions done on behalf of a state or an agent of the state. Detailsmay be provided related to any transaction that impacts an accountbalance, for example benefits associated with a customer 110 orchildcare provider 140. Both a processor identification number and abatch file name associated with the transaction may identify atransaction originator.

[0095] Terminal activity reports 1120 may indicate all transactions thatresult in childcare service being provided to customer 110. Such areport may list the transaction type, the start and end time ofchildcare provided, the transaction date, and the benefits impacted byeach transaction. Clearing report 1130 may provide informationconcerning total funds that are being transferred between, for example,funding agencies and childcare providers 140. Administrative reports1150 includes any other reports related to the administration ofbenefits. Financial reports 1160 may relate to the various financialdata concerning the benefits, which may be arranged in any manner.

[0096]FIG. 12A illustrates an exemplary payment report 1170. Paymentreport 1170 may include provider, facility and contract numberinformation, along with a listing of authorized children associated withvarious customers 110 and attendance for the children during a paymentperiod. FIG. 12B illustrates an exemplary data activity report 1180.Data activity report 1180 may include listings of total changes for aparticular county, for example.

[0097] Methods of Interaction with Childcare Processing System

[0098] Referring now to FIG. 13, a flow chart is shown corresponding toan exemplary method for processing childcare benefits. As shown, themethod may comprise providing a graphical user interface to childcarecustomer 110 for accessing at least account information concerning atleast one benefit type (step 1310). The graphical user interface may beimplemented using a web browser, for example, Microsoft InternetExplorer, Netscape Navigator, or any other similar software. Thegraphical user interface may be made available on a personal computer, ahandheld computer, a television, a thin computer, or any other devicecapable of accessing a network, such as the Internet, via a graphicaluser interface. Interactive functionality may be provided using XML,Java Server Pages, Microsoft Active Server Pages or any other similarcombination of software. For example, using a HTTP server 712 and JSPengine 714, which may be used to act as an intermediary between benefitsdatabase 730 (of FIG. 7) and the childcare customer 110. Using thegraphical user interface, the childcare customer 110 may access at leastaccount information concerning at least one benefit type. The term“account information” as used herein includes, but is not limited to,account balance information, and any other information related to thechildcare customer 110.

[0099] Next, a request from childcare customer 110 through the graphicaluser interface may be received for displaying the at least accountinformation concerning the at least one benefit type (step 1320). Thechildcare customer 110 may request information concerning the at leastone benefit type using any user interface element, such as selecting anitem from a pull-down list, clicking a button, or any other type ofgraphical user interface element.

[0100] As shown in FIG. 13, the at least account information concerningthe at least one benefit type may then be displayed through thegraphical user interface (step 1330). Consistent with this method, suchinformation may be displayed immediately after receiving the request ormay be displayed at a later time. Further, the childcare processingsystem may also display at least one electronic message concerning theat least one benefit type to the childcare customer 110.

[0101]FIG. 14 depicts a flow chart for another exemplary method forprocessing childcare benefits. The method may include childcareprocessing system 200 receiving a request from a childcare customer 110through a graphical user interface for accessing at least transactioninformation concerning at least one type of childcare benefits (step1410). As discussed earlier, in some embodiments the graphical userinterface may be a web browser.

[0102] Next, the childcare processing system may display the accounttransaction information concerning the at least one type of childcarebenefits to the childcare customer 110 through the graphical userinterface (step 1420). The childcare processing system may then receivean inquiry from the childcare customer 110 through the graphical userinterface concerning the displayed account transaction information (step1430).

[0103] The childcare processing system may then respond to the inquiryfrom the childcare customer 110 concerning the displayed accounttransaction information through the graphical user interface (step1440). Although this response may be generated automatically by thechildcare processing system, an operator may manually respond to theinquiry as well.

[0104]FIG. 15 shows a flow chart for an exemplary method for managingchildcare benefits. The exemplary method may include the childcareprocessing system receiving a request from at least one childcareprovider 140, in some embodiments made through a graphical userinterface, for accessing information regarding transactions handled bythe at least one childcare provider 140 concerning at least one type ofchildcare benefit (step 1510). Thus, as part of step 1510, a childcareprovider 140 may access information regarding any transactions that werepaid for using benefit card 120.

[0105] The method may further include displaying the informationregarding the transactions handled by the at least one childcareprovider 140 concerning the at least one type of childcare benefits atthe graphical user interface (step 1520). In some embodiments,information regarding the transactions handled by the at least onechildcare provider 140 may be displayed in a summary form. Additionally,detailed information regarding at least one transaction handled by theat least one childcare provider 140 concerning the at least one type ofchildcare benefits may be displayed. Further, an benefits administrator130 or another authorized user may search information concerning the atleast one childcare provider 140 through the graphical user interface.Further, information regarding transactions for a particular childcareprovider 140, initiated either by childcare provider 140 or benefitsadministrator 130, may be transmitted to childcare provider 140.

[0106]FIG. 16 shows a flow chart for an exemplary method for managingchildcare benefits. Consistent with the exemplary method, a web browserbased administrator terminal may be provided to at least one governmentrepresentative, benefits administrator 130, for managing at least onetype of childcare benefit (step 1610). The government representative maybe a federal, state, or county employee or anyone else authorized tomanage the at least one type of childcare benefits. The method mayfurther include creating an account for at least one childcare customer110 using the web browser based administrative terminal (step 1620). Anadministrator terminal may be similar to terminal 150, but may havefurther functionality associated with the duties of benefitsadministrator 130.

[0107] The method may further include issuing a benefit card to the atleast one childcare customer 110 for the at least one type of childcarebenefits (step 1630). The benefit card may be similar to a credit card,a smart card, or any other type of card and/or apparatus that may beused to access benefits-related information. Thus, for example, as shownin FIG. 10C, a new card may be issued. Further, the authorized user, forexample, a county employee, may add at least one childcare provider 140to the at least one type of childcare benefit. Alternatively, theauthorized user may cancel at least one childcare provider 140 from theprogram.

[0108]FIG. 17 shows a flow diagram illustrating an exemplary method forproviding access to childcare benefits. The exemplary method may includereceiving information identifying a childcare customer 110 from terminal150 (step 1702). The childcare customer 110 may swipe a benefit card atterminal 150, thereby providing information coded on, for example, amagnetic strip.

[0109] Next, the information identifying the childcare customer 110 maybe authenticated (step 1704). Authentication may include verifying thechildcare customer 110's identity. It may further include determiningthe eligibility of the childcare customer 110 to receive a particularbenefit.

[0110] The exemplary method, as shown in FIG. 17, may further includereceiving a request to debit an account corresponding to the childcarecustomer 110 (step 1706). This information may be received beforeauthenticating the information identifying the childcare customer 110.Thus, both the information identifying the childcare customer 110 andthe request to debit the account may be received before authentication.Further, the exemplary method includes processing the request to debitthe account corresponding to the childcare customer 110 (step 1708).This step may include debiting the account and recording the transactionfor reporting purposes.

[0111]FIG. 18 is one exemplary flow diagram illustrating use ofchildcare services consistent with methods and systems of the presentinvention. A start time is recorded (step 1810). The start time may berecorded in response to a prompt on display 517 of terminal 150 to thechildcare customer 110, requesting the entering of account informationvia one of card reader 513 or keypad 515. In some embodiments, oncevalid account information is entered, display 517 prompts childcarecustomer 110 to enter the transaction type. Display 517 presents tochildcare customer 110 a plurality of transactions along with anassigned alphanumeric character. Childcare customer 110 may select atransaction by depressing one of buttons labeled with the correspondingassigned character. When childcare customer 110 selects the transaction,display 517 may prompt the client to enter additional informationrequired to complete the transaction. For example, if childcare customer110 selects the transaction for entering attendance information for aprevious visit, then display 517 prompts childcare customer 110 to inputa date and at least one of a start time or end time for the childcareservices rendered during a previous visit.

[0112] Terminal 150 records an end time in step 1820. When a childcarecustomer 110 returns to childcare provider 140 at the end of the day,they may once again swipe the benefit card and with this action an endtime is recorded. Terminal 150 may then processes the transactioninformation and calculate payment due to childcare provider 140. Thetransaction record 160, including the start time and the end time istransmitted to childcare processing system 200 (step 1830). Childcareprocessing system 200 enables benefits administrator 130 (which mayrepresent a plurality of authorized users) to obtain transactioninformation to be processed by central computer 120 and associated withchildcare provider 140.

[0113] Using record 160, benefits are processed by childcare processingsystem 200 (step 1840). The start time and end time can be used, alongwith childcare customer 110 attributes to determine payments to thechildcare provider 140. Benefits administrator 130 may handle thisprocessing. Benefits administrator 130 may also process payment data andtransaction information for the purposes of auditing providerfacilities, reconciling discrepancies in calculated payments, andprocessing payments.

[0114]FIG. 19 is an exemplary flow diagram illustrating management ofchildcare services consistent with methods and systems of the presentinvention. Benefits administrators 130 may have a need for reports thataudit childcare provider facilities 140, reconciling discrepancies incalculated payments, and processing payments. In order to managechildcare services a record or set of records 160 are received (step1910). Record 160 is then processed so that at least a start time andend time of the childcare service are analyzed (step 1920). At thisstep, benefits administrator 130 may calculate payments for childcareprovider 140, for example, based on the start time and end time of thechildcare service. If the payment due identified in the record does notequal the calculated payment, then childcare provider 140 may be auditedto identify the discrepancy, or reconciliation of the calculated paymentso that the discrepancy is resolved. On the other hand, if the paymentdue equals the calculated payment, then benefit administrator mayauthorize an electronic transfer of funds from a financial institutionto the account of childcare provider 140. A report is then generatedbased on the processed records (step 1930). This report can indicate theresults of auditing or of successful payments to childcare provider 140.

[0115] Other embodiments of the invention will be apparent to thoseskilled in the art from consideration of the specification and practiceof the invention disclosed herein. For example, although the variousembodiments have been described by referring to childcare benefits, theyare applicable for benefits sponsored by private entities and/orbenefits sponsored by a combination of private and public funds.Accordingly, it is intended that the specification and examples beconsidered as exemplary only, with a true scope and spirit of theinvention being indicated by the following claims.

What is claimed is:
 1. A method for processing benefits payments to aservices provider for authorized services provided by the serviceprovider, comprising: issuing a benefit token with a uniquemachine-readable identifier to a customer; reading the identifier fromthe benefit token at a terminal located at the provider at the beginningof a service session to generate a start time; reading the identifierfrom the benefit token at the terminal at the end of the service sessionto generate an end time; transmitting a transaction record including thestart time and the end time to a processing system; computing a benefitpayment based on the start time, the end time, and an eligibilitycriteria; and transmitting the benefit payment to the services provider.2. A method for processing childcare benefits payments to a childcareservices provider for authorized services provided by the childcareservice provider, comprising: issuing a benefit token with a uniquemachine-readable identifier to a customer; reading the identifier fromthe benefit token at a terminal located at the childcare serviceprovider at the beginning of a service session to generate a start time;reading the identifier from the benefit token at the terminal at the endof the service session to generate an end time; transmitting atransaction record including the start time and the end time to aprocessing system; computing a childcare benefit payment based on thestart time, the end time, and an eligibility criteria; and transmittingthe childcare benefit payment to the childcare services provider.
 3. Themethod of claim 2 further comprising: receiving a co-payment amount fromthe customer.
 4. The method of claim 2 further comprising: approving theservice of the childcare services provider.
 5. The method of claim 2wherein recording the start time comprises: recording at least a dateand a time corresponding to the start time.
 6. The method of claim 2wherein recording the end time comprises: recording at least a date anda time corresponding to the end time.
 7. The method of claim 2 furthercomprising: subjecting the payment to at least one business rule.
 8. Themethod of claim 7 wherein the at least one business rule provides atleast one state-specific rule.
 9. The method of claim 8 wherein thestate-specific rule limits the maximum duration for which a childcareservice provider may be paid in a predetermined duration.
 10. The methodof claim 2 wherein the recorded start times and end times are stored atthe terminal.
 11. The method of claim 2 further comprising: receiving arequest from the customer through a graphical user interface foraccessing at least account balance information concerning at least onetype of childcare service; and displaying the at least account balanceinformation concerning the at least one type of childcare service to thecustomer through the graphical user interface.
 12. The method of claim11 wherein the graphical user interface is a web browser interface. 13.The method of claim 2 further comprising: receiving a request from thechildcare service provider through a graphical user interface foraccessing at least one payment; and displaying the at least accountbalance information concerning the at least one payment to the childcareservice provider through the graphical user interface.
 14. The method ofclaim 13 wherein the graphical user interface is a web browserinterface.
 15. The method of claim 13 further comprising: displaying atleast one electronic message concerning the inquiry to the childcareservice provider through the graphical user interface.
 16. The method ofclaim 2 wherein the childcare service provider is an authorizedchildcare service provider.
 17. An apparatus for processing benefits,comprising: an issuing component to issue a benefit token to a customer;a receiving component to receive a start time record for service at aservice provider, the start time record recorded in at a terminallocated at the service provider at the start of service through use ofthe benefit token, and to receive an end time record for service at theservice provider, the end time record recorded at a terminal located atthe service provider at the end of service through use of the benefittoken; a computing component to compute the benefit eligibility based onthe start time record, the end time record, and benefits available forthe customer; and a payment component to pay the service provider apayment based on the computed benefit eligibility.
 18. An apparatus forprocessing childcare benefits, comprising: an issuing component to issuea benefit token to a customer; a receiving component to receive a starttime record for service at a childcare service provider, the start timerecord recorded in at a terminal located at the childcare serviceprovider at the start of service through use of the benefit token, andto receive an end time record for service at the childcare serviceprovider, the end time record recorded at a terminal located at thechildcare service provider at the end of service through use of thebenefit token; a computing component to compute the childcare benefiteligibility based on the start time record, the end time record, andbenefits available for the customer; and a payment component to pay theservice provider a payment based on the computed childcare benefiteligibility.
 19. The apparatus of claim 18 further comprising aco-payment receiving component to receive a co-payment amount from thecustomer.
 20. The apparatus of claim 18 further comprises: an approvingcomponent to approve the service of the childcare service provider. 21.The apparatus of claim 18 wherein the start time record comprises atleast a date and a time corresponding to the start time.
 22. Theapparatus of claim 18 wherein the end time record comprises at least adate and a time corresponding to the end time.
 23. The apparatus ofclaim 18 further comprising a subjecting component to subject thepayment to at least one business rule.
 24. The apparatus of claim 23wherein the at least one business rule provides at least onestate-specific rule.
 25. The apparatus of claim 24 wherein thestate-specific rule limits the maximum duration for which the childcareservice provider may be paid in a predetermined duration.
 26. Theapparatus of claim 18 wherein the start time record and end time recordare stored at the terminal.
 27. The apparatus of claim 18 wherein thechildcare service provider is an authorized childcare service provider.28. A system for processing benefits, comprising: means for issuing abenefit token to a customer; means for receiving a start time forservice at a service provider, the start time recorded by using thebenefit token at a terminal located at the service provider at the startof service; means for receiving an end time for service at the serviceprovider, the end time recorded by using the benefit token at a terminallocated at the service provider at the end of service; means forcomputing a benefit eligibility based on the start time, the end timeand benefits available for the customer; and means for paying theservice provider a payment based on the computed benefit eligibility.29. A system for processing childcare benefits, comprising: means forissuing a benefit token to a customer; means for receiving a start timefor service at a childcare service provider, the start time recorded byusing the benefit token at a terminal located at the childcare serviceprovider at the start of service; means for receiving an end time forservice at the childcare service provider, the end time recorded byusing the benefit token at a terminal located at the childcare serviceprovider at the end of service; means for computing a childcare benefiteligibility based on the start time, the end time and benefits availablefor the customer; and means for paying the service provider a paymentbased on the computed childcare benefit eligibility.
 30. The system ofclaim 29 further comprising: means for receiving a co-payment amountfrom the customer.
 31. The system of claim 29 further comprising: meansfor approving the service of the childcare service provider.
 32. Thesystem of claim 29 wherein the means for recording the start timecomprises: means for recording at least a date and a time correspondingto the start time.
 33. The system of claim 29 wherein the means forrecording the end time comprises: means for recording at least a dateand a time corresponding to the end time.
 34. The system of claim 29further comprising: means for subjecting the payment to at least onebusiness rule.
 35. The system of claim 34 wherein the at least onebusiness rule provides at least one state-specific rule.
 36. The systemof claim 35 wherein the state-specific rule limits the maximum durationfor which the childcare service provider may be paid in a predeterminedduration.
 37. The system of claim 29 further comprising a means forstoring start times and end times at the terminal.
 38. The system ofclaim 29 further comprising: means for receiving a request from thecustomer through a graphical user interface for accessing at leastaccount balance information concerning at least one type of service; andmeans for displaying the at least account balance information concerningthe at least one type of service to the customer through the graphicaluser interface.
 39. The system of claim 38 wherein the graphical userinterface is a web browser interface.
 40. The system of claim 39 furthercomprising: means for receiving a request from the childcare serviceprovider through a graphical user interface for accessing at least onepayment; and means for displaying the at least account balanceinformation concerning the at least one payment to the childcare serviceprovider through the graphical user interface.
 41. The system of claim40 wherein the graphical user interface is a web browser interface. 42.The system of claim 40 further comprising: means for displaying at leastone electronic message concerning the inquiry to the childcare serviceprovider through the graphical user interface.
 43. The system of claim29 wherein the childcare service provider is an authorized childcareservice provider.
 44. A computer-readable medium containing instructionsfor controlling a data processing system to perform a method forprocessing benefits, the method comprising the steps of: issuing abenefit token with a unique machine-readable identifier to a customer;reading the identifier from the benefit token at a terminal located atthe provider at the beginning of a service session to generate a starttime; reading the identifier from the benefit token at the terminal atthe end of the service session to generate an end time; transmitting atransaction record including the start time and the end time to aprocessing system; computing benefit payment based on the start time,the end time, and an eligibility criteria; and transmitting the benefitpayment to the services provider.
 45. A computer-readable mediumcontaining instructions for controlling a data processing system toperform a method for processing childcare benefits, the methodcomprising the steps of: issuing a benefit token with a uniquemachine-readable identifier to a customer; reading the identifier fromthe benefit token at a terminal located at the childcare servicesprovider at the beginning of a service session to generate a start time;reading the identifier from the benefit token at the terminal at the endof the service session to generate an end time; transmitting atransaction record including the start time and the end time to aprocessing system; computing a childcare benefit payment based on thestart time, the end time, and an eligibility criteria; and transmittingthe childcare benefit payment to the childcare services provider. 46.The computer-readable medium of claim 45 further comprising the step of:receiving a co-payment amount from the customer.
 47. Thecomputer-readable medium of claim 45 further comprising the step of:approving the service of the childcare service provider.
 48. Thecomputer-readable medium of claim 45 wherein the step of recording thestart time comprises: recording at least a date and a time correspondingto the start time.
 49. The computer-readable medium of claim 45 whereinthe step of recording the end time comprises: recording at least a dateand a time corresponding to the end time.
 50. The computer-readablemedium of claim 45 further comprising the step of: subjecting thechildcare benefit payment to at least one business rule.
 51. Thecomputer-readable medium of claim 50, wherein the at least one businessrule provides at least one state-specific rule.
 52. Thecomputer-readable medium of claim 50, wherein the state-specific rulelimits the maximum duration for which the childcare service provider maybe paid in a predetermined duration.
 53. The computer-readable medium ofclaim 45, wherein the recorded start times and end times are stored atthe terminal.
 54. The computer-readable medium of claim 45 furthercomprising the step of: receiving a request from the customer through agraphical user interface for accessing at least account balanceinformation concerning at least one type of childcare service; anddisplaying the at least account balance information concerning the atleast one type of childcare service to the customer through thegraphical user interface.
 55. The computer-readable medium of claim 54,wherein the graphical user interface is a web browser interface.
 56. Thecomputer-readable medium of claim 45 further comprising the step of:receiving a request from the childcare service provider through agraphical user interface for accessing at least one payment; anddisplaying the at least account balance information concerning the atleast one payment to the childcare service provider through thegraphical user interface.
 57. The computer-readable medium of claim 56,wherein the graphical user interface is a web browser interface.
 58. Thecomputer-readable medium of claim 56, further comprising: displaying atleast one electronic message concerning the inquiry to the childcareservice provider through the graphical user interface.
 59. Thecomputer-readable medium of claim 45, wherein the childcare serviceprovider is an authorized childcare service provider.
 60. A method formanaging benefits, comprising: providing a web browser basedadministrative terminal to at least one benefits administrator formanaging at least one type of benefit; creating an account for at leastone customer using the web browser based administrative terminal;issuing a benefit token to the at least one customer for at least onetype of service; receiving a transaction record, including a start timeand an end time for service at a service provider for the at least onecustomer; calculating a benefits payments based on the transactionrecord and the at least one type of benefit; and providing payment tothe service provider based on the service.
 61. A method for managingchildcare benefits, comprising: providing a web browser basedadministrative terminal to at least one benefits administrator formanaging at least one type of childcare benefit; creating an account forat least one customer using the web browser based administrativeterminal; issuing a benefit token to the at least one customer for atleast one type of childcare service; receiving a transaction record,including a start time and an end time for service at a childcareservice provider for the at least one customer; calculating a childcarebenefits payment based on the transaction record and the at least onetype of childcare benefit; and providing payment to the childcareservice provider based on the service.
 62. The method of claim 61,further comprising: replacing at least one lost or stolen benefit token.63. The method of claim 61, further comprising: issuing at least onecode corresponding to the benefit token to that at least one customer.64. The method of claim 61, further comprising: storing each transactionrecord regarding the account for the at least one customer for the atleast one type of childcare benefit in at least one record log.
 65. Asystem for managing benefits, comprising: a providing component toprovide a web browser based administrative terminal to at least onebenefits administrator for managing at least one type of benefit; acreating component to create an account for at least one customer usingthe web browser based administrative terminal; a token issuing componentto issue a benefit token to the at least one customer for the at leastone type of service; a receiving component to receive a transactionrecord, including a start time and an end time for service at a serviceprovider for the at least one customer; a calculating component tocalculate a benefits payments based on the transaction record and the atleast one type of benefit; and a payment component to provide to theservice provider based on the service.
 66. A system for managingchildcare benefits, comprising: a providing component to provide a webbrowser based administrative terminal to at least one benefitsadministrator for managing at least one type of childcare benefit; acreating component to create an account for at least one customer usingthe web browser based administrative terminal; a token issuing componentto issue a benefit token to the at least one customer for the at leastone type of childcare service; a receiving component to receive atransaction record, including a start time and an end time for serviceat a childcare service provider for the at least one customer; acalculating component to calculate a childcare benefit payment based onthe transaction record and the at least one type of childcare benefit;and a payment component to provide to the childcare service providerbased on the service.
 67. The method of claim 66, further comprising: areplacing component to replace at least one lost or stolen benefittoken.
 68. The method of claim 66, further comprising: a code issuingcomponent to issue at least one code corresponding to the benefit tokento that at least one customer.
 69. The system of claim 66, furthercomprising: a storing component to store each transaction recordregarding the account for the at least one customer for the at least onetype of childcare benefit in at least one record log.
 70. A system formanaging benefits, comprising: means for providing a web browser basedadministrative terminal to at least one benefits administrator formanaging at least one type of benefit; means for creating an account forat least one customer using the web browser based administrativeterminal; means for issuing a benefit token to the at least one customerfor the at least one type of service; means for receiving a transactionrecord, including a start time and an end time for service at a serviceprovider for the at least one customer; means for calculating a benefitspayments based on the transaction record and the at least one type ofbenefit; and means for providing payment to the service provider basedon the service.
 71. A system for managing childcare benefits,comprising: means for providing a web browser based administrativeterminal to at least one benefits administrator for managing at leastone type of childcare benefit; means for creating an account for atleast one customer using the web browser based administrative terminal;means for issuing a benefit token to the at least one customer for theat least one type of childcare service; means for receiving atransaction record, including a start time and an end time for serviceat a childcare service provider for the at least one customer; means forcalculating a childcare benefit payment based on the transaction recordand the at least one type of childcare benefit; and means for providingpayment to the childcare service provider based on the service.
 72. Thesystem of claim 71 further comprising: means for replacing at least onelost or stolen benefit token.
 73. The system of claim 71 furthercomprising: means for issuing at least one code corresponding to thebenefit token to the at least one customer.
 74. The system of claim 71further comprising: means for storing each transaction record regardingthe account for the at least one customer for the at least one type ofchildcare benefit in at least one record log.
 75. A computer-readablemedium containing instructions for controlling a data processing systemto perform a method for managing benefits, the method comprising thesteps of: providing a web browser based administrative terminal to atleast one benefits administrator for managing at least one type ofbenefit; creating an account for at least one customer using the webbrowser based administrative terminal; issuing a benefit token to the atleast one customer for the at least one type of service; receiving atransaction record, including a start time and an end time for serviceat a service provider for the at least one customer; calculating abenefit payment based on the transaction record and the at least onetype of benefit; and providing payment to the service provider based onthe service.
 76. A computer-readable medium containing instructions forcontrolling a data processing system to perform a method for managingchildcare benefits, the method comprising the steps of: providing a webbrowser based administrative terminal to at least one benefitsadministrator for managing at least one type of childcare benefit;creating an account for at least one customer using the web browserbased administrative terminal; issuing a benefit token to the at leastone customer for the at least one type of childcare service; receiving atransaction record, including a start time and an end time for serviceat a childcare service provider for the at least one customer;calculating a childcare benefit payment based on the transaction recordand the at least one type of childcare benefit; and providing payment tothe childcare service provider based on the service.
 77. Thecomputer-readable medium of claim 76 further comprising the steps of:replacing at least one lost or stolen benefit token.
 78. Thecomputer-readable medium of claim 76 further comprising the steps of:issuing at least one code corresponding to the benefit token to that atleast one customer.
 79. The computer-readable medium of claim 76 furthercomprising the steps of: storing each transaction record regarding theaccount for the at least one customer for the at least one type ofchildcare benefit in at least one record log.
 80. A method for trackingand managing benefit services, comprising: recording start time ofservices provided at each of a plurality of service providers; recordingend time of the services; processing at least the start time and the endtime; computing a payment based on the start time and the end time;making the payment to service providers; and generating a report basedon the processed start time and end time.
 81. A method for tracking andmanaging childcare benefit services, comprising: recording start time ofservices provided at each of a plurality of childcare service providers;recording end time of the services; processing at least the start timeand the end time; computing a payment based on the start time and theend time; making the payment to childcare service providers; andgenerating a report based on the processed start time and end time. 82.The method of claim 81, wherein generating a report comprises:generating at least one of a payment report, a data activity report, andan unusual activity report.
 83. A system for tracking and managingservices, comprising: a recording component to record a start time ofservices provided at each of a plurality of service providers, andrecord an end time of the services; a processing component to process atleast the start time and the end time; a computing component to computea payment based on the start time and the end time; a payment componentto make the payment to service providers; and a report generatingcomponent to generate a report based on the processed start time and endtime.
 84. A system for tracking and managing childcare services,comprising: a recording component to record a start time of servicesprovided at each of a plurality of childcare service providers, andrecord an end time of the services; a processing component to process atleast the start time and the end time; a computing component to computea payment based on the start time and the end time; a payment componentto make the payment to childcare service providers; and a reportgenerating component to generate a report based on the processed starttime and end time.
 85. The system of claim 84, wherein the reportgenerating component comprises a payment report generating component forgenerating a payment report, a data activity report component forgenerating a data activity report, and an unusual activity reportcomponent for generating an unusual activity report.
 86. A system fortracking and managing benefit services, comprising: means forelectronically recording start time of services provided at each of aplurality of providers; means for electronically recording end time ofthe services; means for processing at least the start time and the endtime; means for computing a payment based on the start time and the endtime; means for making the payment to service providers; and means forgenerated a report based on the processed start time and end time.
 87. Asystem for tracking and managing childcare benefit services, comprising:means for electronically recording start time of services provided ateach of a plurality of childcare service providers; means forelectronically recording end time of the services; means for processingat least the start time and the end time; means for computing a paymentbased on the start time and the end time; means for making the paymentto the childcare service providers; and means for generated a reportbased on the processed start time and end time.
 88. The system of claim87, wherein generating a report comprises: means for generating at leastone of a payment report, a data activity report, and an unusual activityreport.
 89. A computer-readable medium containing instructions forcontrolling a data processing system to perform a method for trackingand managing benefit services, the method comprising the steps of:electronically recording start time of services provided at each of aplurality of service providers; electronically recording end time of theservices; processing at least the start time and the end time; computinga payment based on the start time and the end time; making the paymentto service provider; and generated a report based on the processed starttime and end time.
 90. A computer-readable medium containinginstructions for controlling a data processing system to perform amethod for tracking and managing childcare benefit services, the methodcomprising the steps of: electronically recording start time of servicesprovided at each of a plurality of childcare service providers;electronically recording end time of the services; processing at leastthe start time and the end time; computing a payment based on the starttime and the end time; making the payment to the childcare serviceproviders; and generated a report based on the processed start time andend time.
 91. The computer-readable medium of claim 90, whereingenerating a report comprises the steps of: generating at least one of apayment report, a data activity report, and an unusual activity report.